Architecture and implementation of closed user groups and limiting mobility in wireless networks

ABSTRACT

A system for providing advanced voice services (AVS) in wireless communications systems includes a Real-Time Exchange (RTX) that interfaces to a wireless communications network to provide the AVS therein, wherein the AVS comprise Closed User Groups and Limiting Mobility. The Closed User Groups allow a group of users to make and receive calls only to other members of a group, and calls outside of the group are disallowed. The Limiting Mobility uses location information to restrict a mobile unit to service within one or more specified systems, cells or location areas;

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit under 35 U.S.C. Section 119(e) ofthe following co-pending and commonly-assigned patent application:

U.S. Provisional Application Ser. No. 60/705,115, filed on Aug. 3, 2005,by Biswas Deepankar, Krishnakant M. Patel, Giridhar K. Boray, andGorachand Kundu, entitled “ARCHITECTURE AND IMPLEMENTATION OF CLOSEDUSER GROUP AND LIMITING MOBILITY IN WIRELESS NETWORKS,” attorneys'docket number 154.20-US-P1;

which application is incorporated by reference herein.

This application is related to the following co-pending andcommonly-assigned patent applications:

U.S. Utility Application Ser. No. 10/515,556, filed Nov. 23, 2004, byGorachand Kundu, Ravi Ayyasamy and Krishnakant Patel, entitled “DISPATCHSERVICE ARCHITECTURE FRAMEWORK,” attorney docket number G&C 154.4-US-WO,which application claims the benefit under 35 U.S.C. Section 365 of PCTInternational Patent Application Serial Number PCT/US03/16386(154.4-WO-U1), which application claims the benefit under 35 U.S.C.Section 119(e) of U.S. Provisional Patent Application Ser. Nos.60/382,981 (154.3-US-P1), 60/383,179 (154.4-US-P1) and 60/407,168(154.5-US-P1);

U.S. Utility Application Ser. No. 10/564,903, filed Jan. 17, 2006, by F.Craig Farrill, Bruce D. Lawler and Krishnakant M. Patel, entitled“PREMIUM VOICE SERVICES FOR WIRELESS COMMUNICATIONS SYSTEMS,” attorneydocket number G&C 154.7-US-WO, which application claims the benefitunder 35 U.S.C. Section 365 of PCT International Patent ApplicationSerial Number PCT/US04/23038 (154.7-WO-U1), which application claims thebenefit under 35 U.S.C. Section 119(e) of U.S. Provisional PatentApplication Ser. Nos. 60/488,638 (154.7-US-P1), 60/492,650 (154.8-US-P1)and 60/576,094 (154.14-US-P1) and which application is acontinuation-in-part and claims the benefit under 35 U.S.C. Section 119,120 and/or 365 of PCT International Patent Application Serial NumberPCT/US03/16386 (154.4-WO-U1);

U.S. patent application Ser. No. 11/126,587, filed May 11, 2005, by RaviAyyasamy and Krishnakant M. Patel, entitled “ARCHITECTURE, CLIENTSPECIFICATION AND APPLICATION PROGRAMMING INTERFACE (API) FOR SUPPORTINGADVANCED VOICE SERVICES (AVS) INCLUDING PUSH TO TALK ON WIRELESS MS 120AND NETWORKS,” attorney docket number 154.9-US-U1, which applicationclaims the benefit under 35 U.S.C. Section 119(e) of U.S. ProvisionalPatent Application Ser. Nos. 60/569,953 (154.9-US-P1) and 60/579,309(154.15-US-P1), and which application is a continuation-in-part andclaims the benefit under 35 U.S.C. Sections 119, 120 and/or 365 of U.S.patent application Ser. No. 10/515,556 (154.4-US-WO) and PCTInternational Patent Application Serial Number PCT/US04/23038(154.7-WO-U1);

U.S. Utility patent application Ser. No. 11/129,268, filed May 13, 2005,by Krishnakant M. Patel, Gorachand Kundu, Ravi Ayyasamy and Basem Ardah,entitled “ROAMING GATEWAY FOR SUPPORT OF ADVANCED VOICE SERVICES WHILEROAMING IN WIRELESS COMMUNICATIONS SYSTEMS,” attorney docket number154.10-US-U1, which application claims the benefit under 35 U.S.C.Section 119(e) of U.S. Provisional Patent Application Ser. No.60/571,075 (154.10-US-P1), and which application is acontinuation-in-part and claims the benefit under 35 U.S.C. Sections119, 120 and/or 365 of U.S. patent application Ser. No. 10/515,556(154.4-US-WO) and P.C.T. International Patent Application Serial NumberPCT/US04/23038 (154.7-WO-U1);

U.S. patent application Ser. No. 11/134,883, filed May 23, 2005, byKrishnakant Patel, Vyankatesh V. Shanbhag, Ravi Ayyasamy, Stephen R.Horton and Shan-Jen Chiou, entitled “ADVANCED VOICE SERVICESARCHITECTURE FRAMEWORK,” attorney docket number 154.11-US-U1, whichapplication claims the benefit under 35 U.S.C. Section 119(e) of U.S.Provisional Patent Application Ser. Nos. 60/573,059 (154.11-US-P1) and60/576,092 (154.12-US-P1), and which application is acontinuation-in-part and claims the benefit under 35 U.S.C. Sections119, 120 and/or 365 of U.S. patent application Ser. No. 10/515,556(154.4-US-WO), P.C.T. International Patent Application Ser. No.PCT/US04/23038 (154.7-WO-U1), U.S. patent application Ser. No.11/126,587 (154.9-US-U1), and U.S. patent application Ser. No.11/129,268 (154.10-US-U1); and

U.S. patent application Ser. No. 11/136,233, filed May 24, 2005, byKrishnakant M. Patel, Vyankatesh Vasant Shanbhag, and Anand Narayanan,entitled “SUBSCRIBER INFORMATION MODULE (SIM) ENABLING ADVANCED VOICESERVICES (AVS) INCLUDING PUSH TO TALK ON WIRELESS MS 120 AND NETWORKS,”attorney docket number 154.13-US-U1, which application claims thebenefit under 35 U.S.C. Section 119(e) of U.S. Provisional PatentApplication Ser. No. 60/573,780 (154.13-US-P1), and which application isa continuation-in-part and claims the benefit under 35 U.S.C. Sections119, 120 and/or 365 of U.S. patent application Ser. No. 10/515,556(154.4-US-WO), P.C.T. International Patent Application Serial NumberPCT/US04/23038 (154.7-WO-U1), U.S. patent application Ser. No.11/126,587 (154.9-US-U1), and U.S. patent application Ser. No.11/134,883 (154.11-US-U1);

U.S. patent application Ser. No. 11/158,527, filed Jun. 22, 2005, by F.Craig Farrill, entitled “PRESS-TO-CONNECT FOR WIRELESS COMMUNICATIONSSYSTEMS,” attorney docket number 154.16-US-U1, which application claimsthe benefit under 35 U.S.C. Section 119(e) of U.S. Provisional PatentApplication Ser. No. 60/581,954 (154.16-US-P1), and which application isa continuation-in-part and claims the benefit under 35 U.S.C. Sections119, 120 and/or 365 of U.S. patent application Ser. No. 10/515,556(154.4-US-WO) and P.C.T. International Patent Application Ser. No.PCT/US04/23038 (154.7-WO-U1);

U.S. patent application Ser. No. 11/183,516, filed Jul. 18, 2005, byDeepankar Biswaas, entitled “VIRTUAL PUSH TO TALK (PTT) AND PUSH TOSHARE (PTS) FOR WIRELESS COMMUNICATIONS SYSTEMS,” attorney docket number154.17-US-U1, which application claims the benefit under 35 U.S.C.Section 119(e) of U.S. Provisional Patent Application Ser. No.60/588,464 (154.17-US-P1); and

U.S. patent application Ser. No. 11/356,775, filed Feb. 17, 2006, byKrishnakant M. Patel, Bruce D. Lawler, Giridhar K. Boray, andBrahmananda R. Vempati, entitled “ENHANCED FEATURES IN AN ADVANCED VOICESERVICES (AVS) FRAMEWORK FOR WIRELESS COMMUNICATIONS SYSTEMS,” attorneydocket number 154.18-US-U1, which application claims the benefit under35 U.S.C. Section 119(e) of U.S. Provisional Patent Application Ser. No.60/654,271 (154.18-US-P1);

PCT International Patent Application Serial Number PCT/US2006/011628,filed Mar. 30, 2006, by Krishnakant M. Patel, Gorachand Kundu, SameerDharangaonkar, Giridhar K. Boray, and Deepankar Biswas, entitled“TECHNIQUE FOR IMPLEMENTING ADVANCED VOICE SERVICES USING ANUNSTRUCTURED SUPPLEMENTARY SERVICE DATA (USSD) INTERFACE,” attorneydocket number 154.19-WO-U1, which application claims the benefit under35 U.S.C. Section 119(e) of U.S. Provisional Patent Application Ser. No.60/666,424 (154.19-US-P1);

all of which applications are incorporated by reference herein.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates in general to wireless communications systems,and more specifically, to enabling Closed User Groups (CUGs) andLimiting Mobility in wireless communications systems.

2. Description of Related Art

Group-based voice services, such as two-way half-duplex voice callswithin a group or between individuals, also known as “Push-to-Talk,”“Press-to-Talk,” PTT or P2T, have enormous revenue earnings potentialfor wireless networks, such as cellular networks and personalcommunications systems (PCS) networks.

Moreover, the Assignee has introduced Advanced Voice Services (AVS)including improved implementations for P2T, as well as novel group-basedvoice services such as Push-to-Conference (P2C) (also known asConference Call), Upgrade to Conference (upgrade from P2T to P2C),Push-to-Message (P2M) (also known as Instant Voice Messaging or IVM) andgroup SMS (Short Message Service), for wireless mobile units or handsetsand networks. More information on these advanced voice services can befound in the cross-referenced applications identified above.

Notwithstanding these innovations, there is a need in the art for otheradvanced voice services that comply with existing and emerging wirelessstandards and provide superior user experiences. The present inventionaims to satisfy this need by providing enhanced features in advancedvoice services for wireless communications systems.

SUMMARY OF THE INVENTION

To overcome the limitations in the prior art described above, and toovercome other limitations that will become apparent upon reading andunderstanding the present specification, the present invention disclosesa system for providing advanced voice services (AVS) in wirelesscommunications systems. In this system, a Real-Time Exchange (RTX)interfaces to a wireless communications network to provide the AVStherein, wherein the AVS comprise Closed User Groups and LimitingMobility. The Closed User Groups allow a group of users to make andreceive calls only to other members of a group, and calls outside of thegroup are disallowed. The Limiting Mobility uses location information torestrict a mobile unit to service within one or more specified systems,cells or location areas.

BRIEF DESCRIPTION OF THE DRAWINGS

Referring now to the drawings in which like reference numbers representcorresponding parts throughout:

FIG. 1 is a block diagram that illustrates an exemplary embodiment of awireless communications network according to a preferred embodiment ofthe present invention;

FIG. 2 illustrates a proposed architecture for a real-time exchangeaccording to the preferred embodiment of the present invention; and

FIG. 3 is a diagram that illustrates the call flow of a call in a ClosedUser Group, according to a preferred embodiment of the presentinvention.

DETAILED DESCRIPTION OF THE INVENTION

In the following description of the preferred embodiment, reference ismade to the accompanying drawings which form a part hereof, and in whichis shown by way of illustration the specific embodiment in which theinvention may be practiced. It is to be understood that otherembodiments may be utilized as structural changes may be made withoutdeparting from the scope of the present invention.

Overview

The present invention discloses the concept of Closed User Groups (CUGs)for Advanced Voice Services (AVS) in wireless communications networks.CUGs allow a group of users to make and receive calls only within thegroup, wherein calls in or out of the group may be disallowed, exceptfor specified members under specified conditions.

The present invention also discloses the concept of Limiting Mobilityfor Advanced Voice Services (AVS) in wireless communications networks.This functionality uses location information to restrict the mobility ofa handset to within one or more specified systems, cells or locationareas.

Network Architecture

FIG. 1 is a block diagram that illustrates an exemplary embodiment of awireless communications network according to a preferred embodiment ofthe present invention.

Within the network 100, an RTX (Real-Time Exchange) 102, previouslyknown as a Dispatch Gateway (DG), communicates with a MSC (MobileSwitching Center) 104 and PSTN (Public Switched Telephone Network) 106using SS7—ISUP/WIN/CAMEL/MAP (Signaling System 7—Integrated ServicesDigital Network User Part/Wireless Intelligent Network/CustomizedApplications for Mobile Enhanced Logic/Mobile Application Part) messagesat a signaling plane 108. A bearer path 110 implements a TDM (TimeDivision Multiplexing) interface carrying PCM (Pulse Code Modulation) orTFO (Tandem Free Operation) voice frames.

When an AVS subscriber originates an AVS call, the MSC 104 routes thecall to the RTX 102. The MSC 104 also requests the BSC 112 via 116 toestablish a radio traffic path 118 with a mobile station (MS) 120 (alsoknown as a handset or mobile unit) via the BTS (Base TransceiverStation) 122 (as it does for a normal cellular call). At this time, theBSC 112 tries to negotiate TFO (if it is supported) or PCM on a TDM linkwith the far end (in this case, the RTX 102).

At the same time (after the MSC 104 terminates the AVS call request tothe RTX 102), the RTX 102 identifies the terminating users and theirMS-ISDN (Mobile Station-Integrated Services Digital Network) numbers(also known as Mobile Directory Numbers or MDNs). It sends an ISUP callorigination request for each terminating MS 120. It may send requestsdirectly to the MSC 104, PSTN 106 or other terminating network,depending on the routing table configuration for terminating MS-ISDNnumbers. Once the bearer path 110 is established, the RTX 102 begins anegotiation with the far end (e.g., the terminating BSC 112) for eachterminating leg to a MS 120.

Once bearer paths 110 are established for originating and terminatinglegs for an AVS call, the RTX 102 switches (or duplicates) voice framesbetween the originating MS 120 and terminating MS 120.

The RTX 102 may use various other networks, such as an IP network or theInternet/Intranet, for various other purposes. For example, thesenetworks may be used in a toll bypass mode where two RTXs 102 canexchange voice traffic bypassing the PSTN 106. In another example, thesenetworks may be used for registration and presence applications.

Since the MSC 104 will not direct a registration request from a MS 120to the RTX 102 (because it would require changes in the MSC 104), thelatter does not have any information of the registered MS 120. Tocircumvent this issue, a registration and presence application executesin the MS 120 and registers with the RTX 102, after establishing acommunication path with the RTX 102. The RTX 102 also uses this path toupdate the presence information in group members' MS 120 with thenetwork 100 availability of the MS 120 of other members of the group.

During roaming, a Home Location Register (HLR) 124 can be accessed viathe MSC 104. The HLR 124 can be used to track the presence of groupmembers' MS 120 within the network 100 and updates the group members' MS120 with the network 100 availability of the MS 120 of other members ofthe group.

In one embodiment, the SMS (Short Message Service) transport is used tocarry messages between the RTX 102 and the MS 120. Messages arecommunicated between the MS 120 and a SMSC (Short Message ServiceCenter) gateway 126 and between the SMSC gateway 126 and the RTX 102.

Finally, three systems are used by the wireless network 100 operator tomanage the wireless network 100, including an Element Management System(EMS) 128 that maintains network 100 and MS 120 profiles, settings andparameters, an Operational Support System (OSS) 130 that providesoperational and maintenance support for subscribers of the wirelessnetwork 100 and a Customer Support System (CSS) 132 that providescustomer support for the wireless network 100. These systems 128, 130and 132 work together to manage the wireless network 100 and MS 120, asdescribed in more detail below.

Real Time Exchange

FIG. 2 illustrates a proposed architecture for the RTX 102 according tothe preferred embodiment of the present invention.

The architecture includes a Call Processing system 200, Presence Server202, Real-Time Event Processing system 204, one or more Media Managers206, and an SMPP (Short Message Peer-to-Peer) Transport 208, as well asmodules for various SS7 protocols, such as MTP-1 (Message Transfer PartLevel 1) 210, MTP-2 (Message Transfer Part Level 2) 212, MTP-3 (MessageTransfer Part Level 3) 214, ISUP (Integrated Services Digital NetworkUser Part) 216, SCCP (Signaling Connection Control Part) 218, and TCAP(Transactions Capabilities Application Part) 220 protocols.

The Call Processing system 200, Presence Server 202, Media Managers 204,SMPP Transport 206, and other modules communicate across an IP network222. The Real-Time Event Processing system 204 communicates directlywith the Call Processing system 200, Presence Server 202, and themodules for various SS7 protocols. The modules for various SS7 protocolscommunicate with other entities via a SS7 Signaling Link 224. The SMPPTransport 206 communicates with a SMSC (Short Message Service Center)126 using the SMPP protocol 226. The Media Managers 204 communicateamong themselves using the H.110 protocol 228 (or some other protocol,such TCP/IP).

The operation of these various components are described in more detailbelow, as well as in the co-pending and commonly-assigned patentapplications cross-referenced above and incorporated by referenceherein.

The originating MS 120 signals the RTX 102 via the wireless network 100,e.g., by transmitting one or more configured DTMF (Dual Tone MultiFrequency) digits to the RTX 102. The Media Manager systems 206 receivethe DTMF digits and pass the DTMF digits to the Call Processing system200. The Call Processing (CP) system 200 determines whether theoriginating MS 120 has subscribed to the AVS feature before originatingthe AVS call. The Call Processing system 200 also determines whether theoriginating MS 120 and terminating MS 120 have sufficient privilegesbefore originating or terminating the call. Upon confirmation, the CallProcessing system 200 initiates a new AVS call. The Call Processingsystem 200 interacts with the Presence Server 202 and Real-Time EventProcessing system 204 to cause the wireless network 100 to perform callsetup with the terminating MS 120 for the AVS call, and thereafter tomanage the AVS call.

During the AVS call, the Call Processing system 200 interacts with theMedia Manager systems 206 to maintain the H.110 channels 228 and assignany additional H.110 channels 228 required for the AVS call, which mayspan across multiple Media Manager systems 206. During the AVS call, theMedia Manager systems 206 of the RTX 102 are used to mix audio streamsbetween the originating MS 120 and the terminating MS 120, and thendeliver these mixed audio streams to the originating MS 120 and theterminating MS 120. The H.110 channels 228 are used for passing mixedand unmixed audio streams voice between the Media Manager systems 200 asrequired.

Closed User Groups

Closed User Groups (CUGs) allow a group of users to make and receivecalls only within a group identified by a Group Id (also known as aCorporate Id). However, calls in or out of the group are generallydisallowed, except for specified members under specified conditions.

CUGs usually are created by an Administrator via the EMS 128, OSS 130 orCSS 132, which in turn updates the RTX 102. The Administrator hassufficient privileges to add and delete users and groups, with the MDNas the identifier, and to specify the type of privileges for each memberof the group.

For example, in one embodiment, a CUG is comprised of members having“Normal” and “Manager” privileges. In one embodiment, the Normalprivilege member is allowed to make and receive intra-CUG calls only,but is not allowed to make or calls outside the CUG (i.e., no incomingor outgoing calls). In another embodiment, the Normal privilege memberis allowed to make and receive intra-CUG calls, and is allowed toreceive calls from outside the CUG, but is not allowed to make callsoutside the CUG (i.e., no outgoing calls). The Manager privilege memberis allowed to make and receive intra-CUG calls, as well as make andreceive calls outside the CUG (i.e., can make both incoming and outgoingcalls).

Once provisioned with the CUGs, call attempts from the group members aredirected by the MSC 104 to the RTX 102 based on an Origination Trigger.Incoming calls are routed from the terminating MSC 104 to the RTX 102using a Termination Trigger.

The RTX 102 determines whether the call is to be allowed or not(depending on the member privileges). In this regard, the RTX 102performs both calling party and called party analysis before deciding toallow or disallow a call.

Note that, in one embodiment, group members need only enter a shortcode, less than the MDNs (e.g., 333), to identify and call other membersin the group.

Note also that the RTX 102 may also support roaming by CUG members.

Call Flow for CUG Call Processing

FIG. 3 is a diagram illustrating the call flow for a Normal privilegemember calling a Normal or Manager privilege member.

1. The CUG member originates a call at MS-1 120 by dialing the calledparty number.

2. A subscriber-based trigger is set at the MSC 104, wherein the MSC 104sends a Transaction Capabilities Application Part (TCAP) trigger messageto the RTX 102, when the trigger criteria are met. The message includesboth the calling party number and called party number.

3. The RTX 104 analyses the calling party digits and identifies the CUGId of the calling party by querying a member information table. If theCUG Id of the calling party is found, the RTX 102 queries a LocationServer (not shown) to find the home RTX 102 of the called party (fromthe dialed digits) in order to ensure that the called party numberbelongs to the same CUG. If the calling and called parties belong to thesame CUG, then the RTX 102 sends a “Continue” message to the MSC 104;otherwise, the RTX 102 sends a “Release” message to the MSC 104.

4. If the MSC 104 receives a “Continue” message, it proceeds with thecall processing, which includes a Traffic Channel (TCH) Setup with MS-1120; otherwise, if the MSC 104 receives a “Release” message, it ends thecall attempt. The MSC 104 initiates a Location Request (LOCReq) to theHLR 124, in order to retrieve the service profiles for both the calledand calling parties.

5. The HLR 124 responds to the LOCReq with a Location Request Response(LOCReq Resp) to the MSC 104, which includes the service profiles forboth the called and calling parties.

6. The MSC 104 sends another TCAP trigger message to the RTX 102,wherein the message includes the service profiles for both the callingparty number and called party number.

7. The RTX 102 ensures that the called party is in the same CUG from themember profile and does the following checks. If the CUG Id of thecalled party is found, the RTX 102 queries the Location Server to findthe home RTX 102 of the calling party (from calling party digits) inorder to ensure that the calling party number belongs to the same CUG.If the caller and called parties belong to the same CUG, the RTX 102sends a “Continue” message to the MSC 104; otherwise, the TX 102 sends a“Release” message to the MSC 104.

7. If the MSC 104 receives a “Continue” message, it processes the callprocessing; otherwise, if the MSC 104 receives a “Release” message, itends the call attempt.

8. The MSC 104 initiates a paging procedure for the MS-2 120.

9. The MS-1 120 is connected to the MS-2 120, and the conversationproceeds.

Use Cases for a CUG Member Having Normal Privileges

The following describes the use cases for a CUG member having normalprivileges.

A CUG Member (Normal Privileges) Attempts an Intra-CUG Call (AbbreviatedDialing)

1. A CUG member having normal privileges initiates an intra-CUG call bydialing a short dial code of a terminating party who is another memberof the same CUG.

2. The call is connected to the terminating party.

3. The member hears terminating party ringing.

4. The member is able to have a conversation with the terminating party.

A CUG Member (Normal Privileges) Attempts a Call Outside the CUG (FullMDN Dialing)

1. A CUG member having normal privileges attempts a call to aterminating party outside of the CUG. 2. The member hears a CallReject-Tone and the call is dropped.

A CUG Member (Normal Privileges) Attempts an Intra-CUG Call (Full MDNDialing)

1. A CUG member having normal privileges initiates an intra-CUG call bydialing the full MDN of a terminating party who is another member of thesame CUG.

2. The call is connected to the terminating party.

3. The member hears terminating party ringing.

4. The member is able to have a conversation with the terminating party.

A CUG Member (Normal Privileges) is Roaming and Attempts an Intra-CUGCall (Any Dialing)

1. A CUG member having normal privileges initiates an intra-CUG call toa terminating party who is another member of the same CUG while roaming.

2. The call is connected to the CUG member.

3. The member hears terminating party ringing.

4. The member is able to have a conversation with the terminating party.

A CUG Member (Normal Privileges) is Roaming and Attempts a Call Outsidethe CUG

1. A CUG member having normal privileges initiates a call a terminatingparty who is not a member of the same CUG while roaming.

2. The member hears a Call-Reject-Tone and the call is dropped.

There is an Incoming Call to a CUG Member with Normal Privileges

1. The call does not get connected to the CUG member.

2. The originator hears a Call-Reject-Tone or Call-Drop-Tone.

Use Cases for a CUG Member having Manager Privileges

The following describes use cases for a CUG member having managerprivileges.

A CUG Member (Manager Privileges) Attempts an Intra-CUG Call(Abbreviated Dialing)

1. A CUG member having manager privileges initiates an intra-CUG call bydialing a short dial code of a terminating party who is another memberof the same CUG.

2. The call is connected to the terminating party.

3. The member hears terminating party ringing.

4. The member is able to have a conversation with the terminating party.

A CUG Member (Manager Privileges) Attempts a Call Outside the CUG (FullMDN Dialing)

1. A CUG member having manager privileges attempts a call to aterminating party who is not a member of the same CUG.

2. The call is connected to the terminating party.

3. The member hears terminating party ringing.

4. The member is able to have a conversation with the terminating party.

A CUG Member (Manager Privileges) Attempts an Intra-CUG Call (Full MDNDialing)

1. A CUG member having manager privileges initiates an intra-CUG call bydialing the full MDN of a terminating party who is another member of thesame CUG.

2. The call is connected to the terminating party.

3. The member hears terminating party ringing.

4. The member is able to have a conversation with the terminating party.

A CUG Member (Manager Privileges) is Roaming and Attempts an Intra-CUGCall (Any Dialing)

1. A CUG member having manager privileges initiates an intra-CUG call toa terminating party who is another member of the same CUG while roaming.

2. The call is connected to the terminating party.

3. The member hears terminating party ringing.

4. The member is able to have a conversation with the terminating party.

A CUG Member (Manager Privileges) is Roaming and Attempts a Call Outsidethe CUG

1. A CUG member having manager privileges initiates a call to aterminating party who is not a member of the same CUG while roaming.

2. The call is connected to the terminating party.

3. The member hears terminating party ringing.

4. The member is able to have a conversation with the terminating party.

There is an Incoming Call to a CUG Member with Manager Privileges

1. The call is connected to the CUG member.

2. The originator hears ringing.

3. The originator is able to have a conversation with the CUG member.

Limiting Mobility

The Limiting Mobility functionality provided by the RTX 102 relates to ageneral position determination for subscribers. Specifically, the RTXcan obtain the following location information regarding the MS 120:

-   -   The identity of the system serving the MS 120.    -   The identity of the cell serving the MS 120.    -   The identity of the location area serving the MS 120.

Additional location information that may be provided to the RTX 102 caninclude the following attributes of the MS 120:

-   -   Geographic position (M),    -   Specifies position in Latitude, Longitude and Altitude,    -   Generalized Time (M),    -   Position Source (O),    -   Horizontal Velocity (O), and    -   Vertical Velocity (O).

Using this location information, the RTX 120 may restrict the mobilityof the MS 120 within a system, cell or location area. For example, anarea can be defined for a subscriber within which he would be allowedservice, and out of which he would be barred service. This home areacould be a combination of one or more systems, cells or a location areaidentity.

The RTX 102 can determine the location information by communicating withthe HLR 124 using MAP version 3 specifications (MAPv3). Once thelocation information is obtained by the RTX 102, it will take an actionon limiting the mobility of the MS 120 as applicable.

The RTX 102 fetches the location information of either or both theoriginating and terminating MS 120 when a call is attempted. The RTX 102checks the location information against configured mobility informationin making the decision on whether to allow or bar the call.

For the originating MS 120, this location information will beup-to-date, since, when a call is being attempted, the MS 120 would hadalready been paged, and the latest location information would beavailable with the serving HLR 124 or MSC 104.

For the terminating MS 120, the RTX 102 can fetch the last knownposition or ask for the latest location information before barring orallowing the call.

Conclusion

The foregoing description of the preferred embodiment of the inventionhas been presented for the purposes of illustration and description. Itis not intended to be exhaustive or to limit the invention to theprecise form disclosed. Many modifications and variations are possiblein light of the above teaching. It is intended that the scope of theinvention be limited not with this detailed description, but rather bythe claims appended hereto.

1. An apparatus for providing advanced voice services in a wirelessnetwork, comprising: a wireless communications network for making callsto and from mobile units, wherein the calls are initiated by call setupand in-band signaling within the wireless communications network andvoice frames for the calls are switched between the mobile units acrossbearer paths in the wireless communications network; and a real-timeexchange that interfaces to the wireless communications network toprovide the advanced voice services therein, wherein the advanced voiceservices comprise Closed User Groups (CUGs) that allow a group of usersto make and receive calls only to other members of a group, and callsoutside of the group are disallowed; wherein both the real-time exchangeand the mobile units that use the advanced voice services communicatewith each other to provide the advanced voice services for the mobileunits.
 2. The apparatus of claim 1, wherein the group members need onlyenter a short code, less than a mobile directory number, to identify andcall other members in the group.
 3. The apparatus of claim 1, whereinthe group is identified by a Group Id.
 4. The apparatus of claim 1,wherein calls outside of the group are disallowed, except for specifiedmembers under specified conditions.
 5. The apparatus of claim 1, whereina CUG is comprised of members having Normal and Manager privileges. 6.The apparatus of claim 5, wherein a Normal privilege member is allowedto make and receive intra-CUG calls only, but is not allowed to make orreceive calls outside the CUG.
 7. The apparatus of claim 5, wherein aNormal privilege member is allowed to make and receive intra-CUG calls,and is allowed to receive calls outside the CUG, but is not allowed tomake calls outside the CUG.
 8. The apparatus of claim 5, wherein aManager privilege member is allowed to make and receive intra-CUG calls,as well as make and receive calls outside the CUG.
 9. An apparatus forproviding advanced voice services in a wireless network, comprising: awireless communications network for making calls to and from mobileunits, wherein the calls are initiated by call setup and in-bandsignaling within the wireless communications network and voice framesfor the calls are switched between the mobile units across bearer pathsin the wireless communications network; and a real-time exchange thatinterfaces to the wireless communications network to provide theadvanced voice services therein, wherein the advanced voice servicescomprise limiting mobility for the mobile units using locationinformation, thereby restricting a mobile unit to service within one ormore specified systems, cells or location areas; wherein both thereal-time exchange and the mobile units that use the advanced voiceservices communicate with each other to provide the advanced voiceservices for the mobile units.
 10. The apparatus of claim 9, wherein thelocation information comprises an identity of a system serving themobile unit, an identity of a cell serving the mobile unit, and anidentity of a location area serving the mobile unit.
 11. The apparatusof claim 9, wherein the advanced voice services limit the mobility forthe mobile units using location information to restrict the mobile unitto a combination of one or more specified systems, cells or locationareas.
 12. The apparatus of claim 9, wherein the location information isprovided by a home location register.
 13. The apparatus of claim 9,wherein the location information is compared against configured mobilityinformation in determining whether to allow or bar a call by the mobileunit.